Check category: Availability

Check description: Checks whether the cluster ID is identical on all nodes in VCS and SF Oracle RAC clusters.

Check procedure:

• Determines the cluster ID in each system in the SF Oracle RAC cluster.

Check recommendation: The cluster IDs should be identical on all nodes in the SF Oracle RAC cluster.

Check category: Availability

Check description: Checks for Oracle user permissions for the llthosts and llttab files.

Check procedure:

• Identifies all the Oracle users on the system.

Check recommendation: The Oracle user must have permissions to access the /etc/llthosts and /etc/llttab files.

Check category: Availability

Check description: Checks whether the LLT links in the system are cross-connected.

Check procedure:

• Identifies all the LLT links configured on the system.

Check recommendation: It is recommended that the LLT links should not be cross-connected.

Check category: Availability

Check description: Checks speed autonegotiation and MAC address settings for all links.

Check procedure:

• Verifies if the speed settings for all LLT links is same in the system

Check recommendation: All links should have the same speed, autonegotition setting ,and unique MAC address.

Check category: Availability

Check description: Checks whether LMX is running with helper thread DISABLED.

Check procedure:

• Checks whether the LMX helper thread is disabled on the system using the /opt/VRTSvcs/rac/bin/lmxshow command.

Check recommendation: It is recommended that you disable the LMX helper thread on the system.

Check category: Availability

Check description: Checks whether the ODM is configured in cluster mode.

Check procedure:

• Checks whether GAB port d. is up on the node.

Check recommendation: It is recommended to configure ODM in cluster mode for SF Oracle RAC.

Check category: Availability

Check description: Checks if Oracle Process Daemon (oprocd) is not running on the system.

Check procedure:

• Verifies whether the oprocd daemon is stopped on the system.

Check recommendation: It is recommended, you must stop oprocd process inside Storage Foundation for Oracle RAC (SF Oracle RAC) environment.

Check category: Availability

Check description: Checks whether all the nodes in an SF Oracle RAC cluster use the same Oracle database version.

Check procedure:

• Determines the Oracle database version in each system in the SF Oracle RAC cluster.

Check recommendation: It is recommended that all nodes must use the identical Oracle database versions within a cluster.

Check category: Availability

Check description: Checks whether the cssd resource is online.

Check procedure:

• Verifies if the cssd resource is configured under VCS and exists in the CVM service group.

Check recommendation: It si recommended that you configure the cssd resource under VCS. For information on configuring the cssd resource, see the Storage Foundation for Oracle RAC documentation.

Check category: Availability

Check description: Checks if Oracle libraries are properly linked.

Check procedure:

• Verifies the presence of Oracle provided libraries - libskgxn, libskgxp (Oracle 10g only), and libodm.

Check recommendation: It is recommended that on SF Oracle RAC, Oracle-provided libraries libskgxn, libskgxp (Oracle 10g only), and libodm should be linked with Veritas-provided libraries.

Check category: Availability

Check description: Checks if vendor clusterware present on the system.

Check procedure:

• Checks for the presence of non-CRS clusterware.

Check recommendation: It is recommended that you must have SF Oracle RAC clusterware installed on the system.

Check category: Availability

Check description: Checks whether the system architecture type is identical across the SF Oracle RAC cluster.

Check procedure:

• Determines the system architecture type of each system in the SF Oracle RAC cluster.

Check recommendation: All nodes in a cluster must use identical system architectures.

Check category: Availability

Check description: Checks whether the Cluster Server Membership Manager(VCSMM) driver is configured on the system.

Check procedure:

• Verifies whether GAB Port o membership is configured.

Check recommendation: It is recommended that you configure VCSMM for SF Oracle RAC.

Check category: Availability

Check description: Checks existence of low privileged user nobody on the system.

Check procedure:

• Verifies user nobody on all SF Oracle RAC cluster nodes with same uid and gid.

Check recommendation: It is mandatory that you create user nobody on all SF Oracle RAC cluster nodes with same uid and gid. For security reasons Oracle requires user nobody with minimum privileges to perform external jobs.

Check category: Availability

Check description: Checks whether the date and time are synchronized across the cluster.

Check procedure:

• Determines the date and time set on each system in the SF Oracle RAC cluster.

Check recommendation: It is recommended that the date and time settings are identical on all cluster nodes.

Check category: Availability

Check description: Checks if the GAB_START entry in the GAB configuration file is set to 1.

Check procedure:

• Verifies whether the GAB_START entry in the GAB configuration file is set to 0.

Check recommendation: Make sure that the GAB_START entry in the GAB configuration file is set to 1 so that the GAB module is enabled and ready to startup after system reboot.

Check category: Availability

Check description: Checks if any of the private links in the cluster are in the jeopardy state.

Check procedure:

• Checks the network connectivity of the target host with the other hosts in the cluster.

Check recommendation: 1. Determine the connectivity of this node with the remaining nodes in the cluster. Enter:
/sbin/lltstat -nvv
If the status is DOWN this node cannot see that link to the other node(s).
2. Restore connectivity through this private link.
3. Verify that connectivity has been restored. Enter:
# /sbin/gabconfig -a | /bin/grep jeopardy
If this command does not have any output, the link has been restored.

Check category: Availability

Check description: Verifies whether I/O fencing is properly configured for cluster.

Check procedure:

• Determines the fencing mode using the 'vxfenadm' command and verifies whether fencing mode is set to either SCSI-3 or SYBASE or CPS or customized.

Check recommendation: Either I/O fencing is not running on the system or fencing mode is not configured properly. It is recommended to configure I/O fencing with fencing mode configured as per product requirements when using SFCFS to avoid VxFS file system corruption.

Check category: Availability

Check description: Checks whether all the LLT links in the system are full-duplex.This check will be skipped for all bonded interfaces.

Check procedure:

• Identifies all the LLT links configured on the system.

Check recommendation: All the LLT links configured in the system should be full duplex.

Check category: Availability

Check description: Checks for the availability of LLT high-priority links and verifies if they are in the private network.

Check procedure:

• Verifies whether the LLT Links are configured on a private link and as high priority by using the lltstat command.

Check recommendation: It is recommended that you have at least two high-priority LLT links in the private network which is required to configure LLT.

Check category: Availability

Check description: Checks if minimum two links configured as LLT links.

Check procedure:

• Identifies all the LLT links configured on the system.

Check recommendation: To ensure HA, it is mandatory that you should have minimum two links configured as LLT links.

Check category: Availability

Check description: Checks whether the operating system and patch levels are synchronized across the cluster.

Check procedure:

• Determines the operating system and patch levels of each system in the SFRAC cluster.

Check recommendation: All the cluster nodes in a cluster must use the same operating system versions and patch levels.

Check category: Availability

Check description: Checks that packages installed across all the nodes in a cluster are consistent

Check procedure:

• Identifies the packages installed on all the nodess in a cluster.

Check recommendation: Ensure that packages installed on all the nodes in a cluster are consistent and package versions are identical. Inconsistent packages can cause errors in application fail-over.

Check category: Availability

Check description: Checks that the nodes running RAC instances are all the members of the SF Oracle RAC cluster. Check uses /etc/llthosts and olsnodes output for comparison.

Check procedure:

• Determines the SF Oracle RAC host membership by reading the /etc/llthosts file.

Check recommendation: The SF Oracle RAC membership and Oracle Clusterware membership must be equal.

Check category: Availability

Check description: Checks whether the number of keys on the coordinator disks equals the number of fencing disks on each node in the cluster.

Check procedure:

• Determines the number of keys on the coordinator disks.

Check recommendation: It is recommended that the number of keys on the coordinator disks should be equal to the number of fencing disks on each node in the cluster.

Check category: Availability

Check description: Checks whether the fencing module is configured properly on all nodes in the cluster.

Check procedure:

• Identifies the product installed - Storage Foundation for Oracle RAC (SF Oracle RAC) or Storage Foundation Cluster File System for Oracle RAC (SFCFSRAC).

Check recommendation: You must configure fencing configuration for SF Oracle RAC. It is recommended configuring fencing in enabled mode for SF Oracle RAC and in disabled mode for SFCFSRAC.

Check category: Availability

Check description: Checks configuration for coordination point server based fencing on all nodes in the cluster.

Check procedure:

• Checks ping status for coordination point server from all nodes in the cluster.

Check recommendation: You must configure fencing for Storage Foundation for Oracle RAC(SF Oracle RAC). It is recommended to configure fencing in enabled mode for SF Oracle RAC.

Check category: Availability

Check description: Checks whether all the Low Latency Transport(LLT) links in the Storage Foundation for Oracle RAC(SF Oracle RAC) node have mtu size set between 1500 and 9000 bytes.

Check procedure:

• Identifies all the LLT links configured in the system.

Check recommendation: All the llt links in the node should have mtu size between 1500 and 9000 bytes.

Check category: Availability

Check description: Checks whether all the Low Latency Transport (LLT) links in the Storage Foundation for Oracle RAC (SF Oracle RAC) cluster have identical mtu size.

Check procedure:

• Identifies all the LLT links configured in the system.

Check recommendation: All the nodes in the cluster should have the same mtu size.

Check category: Best practices

Check description: Checks whether the installed Storage Foundation / InfoScale products are at the latest software patch level.

Check procedure:

• Identifies all the Storage Foundation / InfoScale products installed on the system.

Check recommendation: To avoid known risks or issues, it is recommended that you install the latest versions of the Storage Foundation / InfoScale products on the system.